docs: update handoff & runtime-resolution pages — handoffs now always route through agent.chat()#825
Conversation
Qodo reviews are paused for this user.Troubleshooting steps vary by plan Learn more → On a Teams plan? Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center? |
|
Warning Review limit reached
More reviews will be available in 54 minutes and 30 seconds. Learn how PR review limits work. Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file). ⌛ How to resolve this issue?After more reviews become available, a review can be triggered using the To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits. 🚦 How do rate limits work?CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan refill rate. For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window. Please see our Fair Usage Limits Policy for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Run ID: 📒 Files selected for processing (2)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
There was a problem hiding this comment.
Code Review
This pull request updates the documentation for agent handoffs and the runtime-resolution subsystem to clarify that handoffs now bypass the runtime-resolution subsystem and directly delegate to the target agent's chat() or achat() pipeline. This ensures that the full pipeline, including instructions, backstory, memory, hooks, guardrails, and tool policies, is preserved. Feedback has been provided to improve the clarity of the tool policy description in the handoffs documentation table and to correct a potentially misleading label in the runtime-resolution sequence diagram.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
| | Memory | The target agent can recall prior interactions | | ||
| | Hooks | Pre/post-call hooks execute normally | | ||
| | Guardrails | Safety policies are always enforced | | ||
| | Tool policy | The `HandoffToolPolicy` intersection is applied on top of the agent's own tools | |
There was a problem hiding this comment.
The description in the 'Why it matters' column for 'Tool policy' explains the mechanism rather than the benefit. To improve clarity, consider rephrasing it to focus on the security aspect.
| Tool policy | Enforces secure and controlled tool access for the target agent |
| TargetRuntime-->>Resolver: runtime instance | ||
| Resolver-->>Handoff: cached & returned | ||
| RuntimeSubsystem->>RuntimeSubsystem: create LLMRuntimeWrapper | ||
| RuntimeSubsystem->>Cache: store & return |
There was a problem hiding this comment.
In the sequence diagram, the label store & return for the interaction from RuntimeSubsystem to Cache could be misinterpreted. It suggests the cache is returning a value, but the arrow indicates a message to the cache. For clarity, consider relabeling this to simply reflect the action of storing the runtime instance.
RuntimeSubsystem->>Cache: store(runtime)
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Workflows to automatically generate PRs for you. |
1 participant
Summary
Fixes #823. Updates two docs pages to reflect that handoffs now always route through agent.chat() / agent.achat() — they no longer invoke resolve_runtime or a bare LLM runtime path. This corrects documentation that described the old broken execution path.
Reference: upstream PR MervinPraison/PraisonAI#2178.
Changes:
docs/features/handoffs.mdx
docs/features/runtime-resolution.mdx (Option A — repositioned)
Cross-link grep: Only handoffs.mdx and runtime-resolution.mdx had the incorrect wording. No edits to docs/concepts/.
Generated with Claude Code